<html>
<head><meta charset="utf-8"><title>adding an aarch64_be-unknown-linux-gnu target · t-compiler · Zulip Chat Archive</title></head>
<h2>Stream: <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/index.html">t-compiler</a></h2>
<h3>Topic: <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html">adding an aarch64_be-unknown-linux-gnu target</a></h3>

<hr>

<base href="https://rust-lang.zulipchat.com">

<head><link href="https://rust-lang.github.io/zulip_archive/style.css" rel="stylesheet"></head>

<a name="137072373"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137072373" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137072373">(Nov 02 2018 at 18:15)</a>:</h4>
<p>I've been slowly stumbling my way through adding support for arm64 big endian to rust/rustc, but I've kind of hit a wall at the moment.<br>
What I'm currently doing is attempting to cross compile rust for aarch64_be.  </p>
<p>I have a Gentoo host which has an aarch64_be cross compiler built on it.  I've added the target, and I'm currently attempting to build rust and I can build my own amd64 rustc which does have the aarch64_be-unknown-linux-gnu target in it, however I'm stuck trying to figure out how to use that built version as the one to build the aarch64_be version.</p>
<p>The following may be overkill, but unfortunately the documentation for adding a target seems to be lacking (or at least, I couldn't find anything with my searches, aside from an issue where someone was working on the documentation but got bored with it so stopped.)</p>
<p>My source checkout is /storage/rust/rust, and everything that is built, is in /storage/rust/build.  I run the following commands from /storage/rust.</p>
<div class="codehilite"><pre><span></span>CC_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-gcc AR_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-ar CXX_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-g++ LD_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-ld ARCH=x86_64 BUILD=x86_64-unknown-linux-gnu HOST=aarch64_be-unknown-linux-gnu PREFIX=x86_64-unknown-linux-gnu  SRC_DIR=/storage/rust/rust /storage/rust/rust/configure --enable-ccache --enable-ninja --full-bootstrap --host=$HOST

nice $SRC_DIR/x.py build src/llvm --host $BUILD

nice $SRC_DIR/x.py build src/rustc --host $HOST
</pre></div>


<p>This seems to do the correct thing, except when I get to the part where it tries to build for $HOST, the stage0 it tries to use is still the one downloaded, which doesn't have the aarch64_be-unknown-linux-gnu target in it.  What I'm trying to figure out and haven't been able to, is how to point it to the compiler I've just built?  I'm assuming I can use --local-rust-root=/storage/rust/build/$something but I'm not sure what $somethiing should be, or if I'm even along the right path.</p>
<p>Any help would be greatly appreciated.</p>
<p>The output I get, when I am attempting to run the above commands is:</p>
<div class="codehilite"><pre><span></span>Updating only changed submodules
Submodules updated in 0.08 seconds
    Finished dev [unoptimized] target(s) in 0.37s
Building stage0 std artifacts (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.37s
Copying stage0 std from stage0 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Building stage0 test artifacts (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.35s
Copying stage0 test from stage0 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.43s
Copying stage0 rustc from stage0 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Building stage0 codegen artifacts (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu, llvm)
    Finished release [optimized] target(s) in 0.30s
Assembling stage1 compiler (x86_64-unknown-linux-gnu)
Building stage1 std artifacts (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.31s
Copying stage1 std from stage1 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / aarch64_be-unknown-linux-gnu)
Building stage1 test artifacts (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.35s
Copying stage1 test from stage1 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / aarch64_be-unknown-linux-gnu)
Building stage1 std artifacts (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.30s
Copying stage1 std from stage1 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu)
Building stage1 compiler artifacts (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu)
    Finished release [optimized] target(s) in 0.42s
Copying stage1 rustc from stage1 (x86_64-unknown-linux-gnu -&gt; x86_64-unknown-linux-gnu / aarch64_be-unknown-linux-gnu)
Building stage1 codegen artifacts (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu, llvm)
    Finished release [optimized] target(s) in 0.34s
Assembling stage2 compiler (aarch64_be-unknown-linux-gnu)
Uplifting stage1 std (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu)
Copying stage2 std from stage1 (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu / aarch64_be-unknown-linux-gnu)
Building stage0 std artifacts (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu)
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn&#39;t exit successfully: `/storage/rust/build/bootstrap/debug/rustc - --crate-name ___ --print=file-names --target aarch64_be-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 1)
--- stderr
error: Error loading target specification: Could not find specification for target &quot;aarch64_be-unknown-linux-gnu&quot;
  |
  = help: Use `--print target-list` for a list of built-in targets


command did not execute successfully: &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo&quot; &quot;build&quot; &quot;--target&quot; &quot;aarch64_be-unknown-linux-gnu&quot; &quot;-j&quot; &quot;8&quot; &quot;--release&quot; &quot;--features&quot; &quot;panic-unwind jemalloc backtrace&quot; &quot;--manifest-path&quot; &quot;/storage/rust/rust/src/libstd/Cargo.toml&quot; &quot;--message-format&quot; &quot;json&quot;
expected success, got: exit code: 101
thread &#39;main&#39; panicked at &#39;cargo must succeed&#39;, bootstrap/compile.rs:1112:9
note: Run with `RUST_BACKTRACE=1` for a backtrace.
failed to run: /storage/rust/build/bootstrap/debug/bootstrap build src/rustc --host=aarch64_be-unknown-linux-gnu
Build completed unsuccessfully in 0:00:06```
</pre></div>



<a name="137073380"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137073380" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> nikomatsakis <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137073380">(Nov 02 2018 at 18:29)</a>:</h4>
<p>cc <span class="user-mention" data-user-id="116015">@Alex Crichton</span>, who <em>probably</em> knows the most about adding new targets? Certainly I would expect <span class="user-mention" data-user-id="116015">@Alex Crichton</span> to know the answer to this:</p>
<blockquote>
<p>What I'm trying to figure out and haven't been able to, is how to point it to the compiler I've just built? I'm assuming I can use --local-rust-root=/storage/rust/build/$something but I'm not sure what $somethiing should be, or if I'm even along the right path.</p>
</blockquote>



<a name="137073770"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137073770" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137073770">(Nov 02 2018 at 18:34)</a>:</h4>
<p><span class="user-mention" data-user-id="134454">@Steev</span> the <code>--local-rust-root</code> should be the same as <code>rustc --print sysroot</code>, aka the folder containing <code>bin</code> which in turns contains <code>rustc</code></p>



<a name="137073796"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137073796" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137073796">(Nov 02 2018 at 18:35)</a>:</h4>
<p>and that may fix your issue?</p>



<a name="137074896"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137074896" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137074896">(Nov 02 2018 at 18:52)</a>:</h4>
<p>It doesn't seem to.  I've added everything to a script here, my script looks like the following:</p>
<div class="codehilite"><pre><span></span>main() {
    #ARCH=aarch64_be
    ARCH=x86_64
    BUILD=x86_64-unknown-linux-gnu
    HOST=aarch64_be-unknown-linux-gnu
    #HOST=x86_64-unknown-linux-gnu
    PREFIX=x86_64-unknown-linux-gnu
    CC_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-gcc
    AR_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-ar
    CXX_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-g++
    LD_aarch64_be_unknown_linux_gnu=aarch64_be-unknown-linux-gnu-ld
    RUSTC_LINKER=aarch64_be-unknown-linux-gnu-gcc

   $SRC_DIR/configure \
       --enable-ccache \
       --enable-ninja \
       --enable-rustbuild \
       --local-rust-root=/storage/rust/build/x86_64-unknown-linux-gnu/stage2/ \
       --enable-local-rebuild \
       --full-bootstrap \
       --host=$HOST

   # work around rust-lang/rust#38037
   nice $SRC_DIR/x.py build src/llvm --host=$BUILD

   # STDOUT
   # Building LLVM for x86_64-unknown-linux-gnu

   nice $SRC_DIR/x.py build src/rustc --host=$HOST
</pre></div>


<p>And I get </p>
<div class="codehilite"><pre><span></span>Building stage0 std artifacts (x86_64-unknown-linux-gnu -&gt; aarch64_be-unknown-linux-gnu)
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn&#39;t exit successfully: `/storage/rust/build/bootstrap/debug/rustc - --crate-name ___ --print=file-names --target aarch64_be-unknown-linux-gnu --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 1)
--- stderr
error: Error loading target specification: Could not find specification for target &quot;aarch64_be-unknown-linux-gnu&quot;
  |
  = help: Use `--print target-list` for a list of built-in targets


command did not execute successfully: &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0/bin/cargo&quot; &quot;build&quot; &quot;--target&quot; &quot;aarch64_be-unknown-linux-gnu&quot; &quot;-j&quot; &quot;8&quot; &quot;--release&quot; &quot;--features&quot; &quot;panic-unwind jemalloc backtrace&quot; &quot;--manifest-path&quot; &quot;/storage/rust/rust/src/libstd/Cargo.toml&quot; &quot;--message-format&quot; &quot;json&quot;
expected success, got: exit code: 101
thread &#39;main&#39; panicked at &#39;cargo must succeed&#39;, bootstrap/compile.rs:1112:9
note: Run with `RUST_BACKTRACE=1` for a backtrace.
failed to run: /storage/rust/build/bootstrap/debug/bootstrap build src/rustc --host=aarch64_be-unknown-linux-gnu
Build completed unsuccessfully in 0:00:06
</pre></div>


<p>Still.  Someone on discord mentioned using the cargo.toml to set the rustc to use, but I'm not sure how the interaction works between using the configure script and the cargo.toml file.</p>



<a name="137081054"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137081054" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137081054">(Nov 02 2018 at 20:40)</a>:</h4>
<p><span class="user-mention" data-user-id="116015">@Alex Crichton</span> so... no go.  Every time it goes to create the stage0 std artifacts, it uses the /storage/rust/build/bootstrap/debug/rustc.</p>
<div class="codehilite"><pre><span></span># Instead of downloading the src/stage0.txt version of the compiler
# specified, use this rustc binary instead as the stage0 snapshot compiler.
rustc = &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage2/bin/rustc&quot;
</pre></div>


<p>At this point, I have no idea.  I don't really understand why the bootstrapped rustc doesn't have the target in it, but the stage2 one does.</p>



<a name="137081212"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137081212" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137081212">(Nov 02 2018 at 20:43)</a>:</h4>
<p><span class="user-mention" data-user-id="134454">@Steev</span> oh the <code>.../bootstrap/debug/rustc</code> isn't the actual rustc that's used, it's just a thin wrapper. If you pass <code>-vv</code> to <code>./x.py build</code> you should see the real rustc being used somewhere in the output. Specifying that <code>rustc</code> should work as well though. Have you tried running the rustc manually to make sure it supports the target in question?</p>



<a name="137081441"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137081441" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137081441">(Nov 02 2018 at 20:46)</a>:</h4>
<p>(deleted)</p>



<a name="137082115"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137082115" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137082115">(Nov 02 2018 at 20:56)</a>:</h4>
<p><span class="user-mention" data-user-id="116015">@Alex Crichton</span> Okay, yes, it's still using the stage0 - </p>
<div class="codehilite"><pre><span></span>rustc command: &quot;LD_LIBRARY_PATH&quot;=&quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0-sysroot/lib:&quot; &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0/bin/rustc&quot; &quot;-&quot; &quot;--crate-name&quot; &quot;___&quot; &quot;--print=file-names&quot; &quot;--target&quot; &quot;aarch64_be-unknown-linux-gnu&quot; &quot;--crate-type&quot; &quot;bin&quot; &quot;--crate-type&quot; &quot;rlib&quot; &quot;--crate-type&quot; &quot;dylib&quot; &quot;--crate-type&quot; &quot;cdylib&quot; &quot;--crate-type&quot; &quot;staticlib&quot; &quot;--crate-type&quot; &quot;proc-macro&quot; &quot;--cfg&quot; &quot;stage0&quot; &quot;--sysroot&quot; &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0-sysroot&quot; &quot;-Cprefer-dynamic&quot; &quot;-Clinker=aarch64_be-unknown-linux-gnu-gcc&quot; &quot;-C&quot; &quot;debug-assertions=n&quot; &quot;-C&quot; &quot;link-args=-Wl,-rpath,$ORIGIN/../lib&quot; &quot;-Z&quot; &quot;force-unstable-if-unmarked&quot;
sysroot: &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0-sysroot&quot;
libdir: &quot;/storage/rust/build/x86_64-unknown-linux-gnu/stage0-sysroot/lib&quot;
error: Error loading target specification: Could not find specification for target &quot;aarch64_be-unknown-linux-gnu&quot;
</pre></div>


<div class="codehilite"><pre><span></span>steev@oswin /storage/rust $ ./build/x86_64-unknown-linux-gnu/stage2/bin/rustc --print target-list | grep aarch64
aarch64-fuchsia
aarch64-linux-android
aarch64-pc-windows-msvc
aarch64-unknown-cloudabi
aarch64-unknown-freebsd
aarch64-unknown-hermit
aarch64-unknown-linux-gnu
aarch64-unknown-linux-musl
aarch64-unknown-netbsd
aarch64-unknown-none
aarch64-unknown-openbsd
aarch64_be-unknown-linux-gnu
</pre></div>


<p>(sorry if this got sent twice, I'm still trying to figure out zulip)</p>



<a name="137083575"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137083575" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137083575">(Nov 02 2018 at 21:22)</a>:</h4>
<p><span class="user-mention" data-user-id="134454">@Steev</span> this may be a bug in rustbuild then?</p>



<a name="137083578"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137083578" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137083578">(Nov 02 2018 at 21:22)</a>:</h4>
<p>I'm not sure :(</p>



<a name="137089598"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137089598" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137089598">(Nov 02 2018 at 23:32)</a>:</h4>
<p><span class="user-mention" data-user-id="116015">@Alex Crichton</span> so, i did something hacky and worked around the issue by taking the x86_64 rustc toolchain that i'd built, and installed it to a temporary directory and then once the install finished, moved it into the stage0 directory...  this appears to be working, so while it's not ideal, it is a bit of a workaround.</p>



<a name="137126418"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/137126418" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Steev <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#137126418">(Nov 03 2018 at 19:58)</a>:</h4>
<p><span class="user-mention" data-user-id="116015">@Alex Crichton</span> i think i'm going about this the wrong way - ideally, i'd be able to point the build at my freshly built toolchain, but perhaps I should instead send a pull request enabling aarch64_be as a target first, and then deal with trying to get aarch64_be building as a host?</p>



<a name="146806090"></a>
<h4><a href="https://rust-lang.zulipchat.com#narrow/stream/131828-t-compiler/topic/adding%20an%20aarch64_be-unknown-linux-gnu%20target/near/146806090" class="zl"><img src="https://rust-lang.github.io/zulip_archive/assets/img/zulip.svg" alt="view this post on Zulip" style="width:20px;height:20px;"></a> Alex Crichton <a href="https://rust-lang.github.io/zulip_archive/stream/131828-t-compiler/topic/adding.20an.20aarch64_be-unknown-linux-gnu.20target.html#146806090">(Nov 05 2018 at 16:17)</a>:</h4>
<p><span class="user-mention" data-user-id="134454">@Steev</span> yeah adding the target first probably makes sense! We can take the other issues from there</p>



<hr><p>Last updated: Aug 07 2021 at 22:04 UTC</p>
</html>